feat(runtime-host): schedule managed update reconciliation - #3750

Summary

• install an OS-owned hourly wake-up for each Maka-managed Runtime Host deployment on Linux (systemd --user) and macOS (LaunchAgent)
• keep the user-selected cadence in the installation-scoped update policy: automatic policies accept 1h through 168h and default to 6h; manual performs no registry discovery or mutation
• gate scheduled invocations before registry access, while an explicit service reconcile-update remains an immediate user-requested check
• reuse feat(runtime-host): add managed update reconciliation #3720's stable managed operator, exact candidate discovery, compatibility admission, active-work boundary, and update transaction instead of introducing an updater daemon or a second mutation authority
• compose scheduler install, verification, logs, rollback, repair, and uninstall with the existing service lifecycle; version cutover does not rewrite the stable schedule
• spread hourly wake-ups and due phases deterministically by installation identity, and normalize pre-cadence policy records to the 6h default

Only a Maka-managed deployment receives this schedule. A transient npx invocation does not become background update authority by itself; an explicit managed setup does. Persistent global-CLI services and SSH clients do not acquire replacement or remote deployment authority.

Builds on #3720, now merged. This branch is rebased onto the merge and contains only the scheduler/cadence change.

Refs #3228
Refs #3709

Verification

• npm --workspace maka-agent test — 457 passed after rebasing onto merged feat(runtime-host): add managed update reconciliation #3720
• npm run lint
• npm run format:check
• npm run typecheck (after building the UI declarations required by Desktop)
• npm run check:asf-headers

Review focus

• the OS scheduler is only a wake-up adapter; the update policy remains the cadence authority
• scheduled manual and not-due paths return before registry access
• lifecycle rollback and uninstall remove the scheduler without allowing a remote Client, PID, version, or Host epoch to become deployment authority

AI use

Select exactly one:

• No generative tool made a substantive contribution
• Generative tooling made a substantive contribution

Tool(s) and scope: OpenAI Codex implemented, tested, documented, and simplified the change under maintainer direction. Human review is required before merge.

Checklist

• Tests cover the change and fail without it
• Lint, format, typecheck and the affected suites pass locally

Does this PR entail a change in behavior?

• Yes — described under Summary above
• No

摘要

• 为 Linux（systemd --user）与 macOS（LaunchAgent）上的每个 Maka 托管 Runtime Host deployment 安装由操作系统持有的每小时唤醒任务
• 检查周期仍由 installation-scoped update policy 持有：自动策略可配置 1h 至 168h，默认 6h；manual 不执行 registry discovery 或 mutation
• 定时调用会在访问 registry 前判断是否到期；用户显式执行 service reconcile-update 则始终立即检查
• 复用 feat(runtime-host): add managed update reconciliation #3720 的稳定 managed operator、精确候选发现、兼容性准入、active-work 边界与 update transaction，不新增 updater daemon 或第二个 mutation authority
• 将 scheduler 的安装、校验、日志、回滚、repair 与 uninstall 组合进现有 service lifecycle；版本切换不重写稳定 schedule
• 按 installation identity 确定性分散每小时唤醒时间与到期 phase；旧版无周期字段的 policy 读取为默认 6h

只有 Maka 托管的 deployment 会获得该 schedule。一次临时 npx 调用本身不会成为后台更新 authority；用户显式执行 managed setup 才会创建它。持久全局 CLI service 与 SSH Client 都不会因此获得替换或 remote deployment authority。

基于已经合入的 #3720；当前分支已 rebase 到其 merge 之后，只包含 scheduler/cadence 变更。

关联 #3228
关联 #3709

验证

• npm --workspace maka-agent test — rebase 到已合入的 feat(runtime-host): add managed update reconciliation #3720 后 457 项通过
• npm run lint
• npm run format:check
• npm run typecheck（先构建 Desktop 所需的 UI declaration）
• npm run check:asf-headers

审查重点

• OS scheduler 只是 wake-up adapter，update policy 才是检查周期 authority
• manual 与尚未到期的定时路径都会在访问 registry 前返回
• lifecycle rollback 与 uninstall 会移除 scheduler，且 remote Client、PID、version、Host epoch 都不会因此成为 deployment authority

AI 使用

OpenAI Codex 在维护者指导下实现、测试、撰写文档并简化本次变更；合入前仍需人工审查。

Checklist

• 测试覆盖新增行为，并能在缺少实现时失败
• lint、format、typecheck 与受影响测试均已在本地通过
• 本 PR 会改变行为，具体见上方摘要